Branch cut updates#3645
Conversation
✅ Deploy Preview for react-native ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
b9c4b29 to
6da53c0
Compare
601402f to
7bb8dd2
Compare
| The packages in the `react-native` monorepo should be always one minor version ahead of the latest or RC version. Once you're done with releasing the initial RC0, you should: | ||
|
|
||
| - Create a new branch in `react-native` from `main` in your own fork. | ||
| - Run `npm run bump-all-updated-packages --release-branch-cutoff` to bump the minor versions of all packages. |
There was a problem hiding this comment.
| - Run `npm run bump-all-updated-packages --release-branch-cutoff` to bump the minor versions of all packages. | |
| - Run `npm run bump-all-updated-packages -- --release-branch-cutoff` to bump the minor versions of all packages. |
For npm we need to add explicit --, because node accepts arguments in a form like --<arg>
There was a problem hiding this comment.
This is not true for yarn, though. So we can change in to yarn bump-all-updated-packages --release-branch-cutoff or provide both variants.
|
|
||
| #### How to execute | ||
|
|
||
| `npm run bump-all-updated-packages` or `npm run bump-all-updated-packages --release-branch-cutoff` |
There was a problem hiding this comment.
| `npm run bump-all-updated-packages` or `npm run bump-all-updated-packages --release-branch-cutoff` | |
| `npm run bump-all-updated-packages` or `npm run bump-all-updated-packages -- --release-branch-cutoff` |
There was a problem hiding this comment.
I used yarn instead since that's the tool of choice for other commands such as running test-e2e-local
There was a problem hiding this comment.
I used
yarninstead since that's the tool of choice for other commands such as runningtest-e2e-local
Can you please update examples of executing this command with yarn? I don't have a strong opinion on if we should include both, seems pretty straightforward, but definitely better for it to be either yarn or npm everywhere
There was a problem hiding this comment.
Fair point, done 👍
|
|
||
| - Add and commit the extra file that got created at `sdks/hermes/.hermesversion`. | ||
|
|
||
| - Update packages in the monorepo by running `npm run bump-all-updated-packages`. All the package bumps should be a patch. Read more about the script and how they work [here](./release-updating-packages). |
There was a problem hiding this comment.
Can we add one more sentence on why we need to do it?
Maybe something like "We need to publish the latest available changes in our code, so they will be included in a new RC"
d8f24c7 to
fe8da5e
Compare
kelset
left a comment
There was a problem hiding this comment.
Good stuff, thanks for working on this @fortmarek! I've left a few suggestions improvements and one main change that I think will make the guide more streamlined.
| - Update packages in the monorepo by running `yarn bump-all-updated-packages`. All the package bumps should be a patch. We need to publish the latest package changes, so they will be included in a new RC. Read more about the script and how they work [here](./release-updating-packages). | ||
| - Push the commit created by the previous command to the `0.x-stable` branch. | ||
|
|
||
| ### 2. Push the branch and test the current changes |
There was a problem hiding this comment.
I just noticed that in this guide we only push the branch up at this step 2.
Maybe let's change this second step to be part of step 1, and separate the Hermes bump into its own step and the bump all packages into its own step too?
There was a problem hiding this comment.
I created separate steps for Hermes and monorepo packages bumps.
I kept this step as a separate one that we should still run only after Hermes + packages bumps as I don't think it's necessary to push multiple times? Or do you see the workflow as:
- Create new branch, push its current state
- Hermes bump
- monorepo bumps
- push the changes again
19c5917 to
bc4a88b
Compare
|
LGTM thanks @fortmarek - can you just fix the lint error? Then @Simek this can be merged 👍 |
bc4a88b to
9c1cfdc
Compare
| This page contains relevant information about how to update packages in the `react-native` [monorepo](https://github.com/react-native-community/discussions-and-proposals/pull/480). | ||
|
|
There was a problem hiding this comment.
Not sure if linking RFC add anything useful for the page context.
Simek
left a comment
There was a problem hiding this comment.
Just one nit about RFC link, other than that LGTM! 👍
Let's cross-check with someone form Meta before landing this tho.
0.72branch cut off and RC0 release with the new steps to update and align packages on the new monorepo setup